IBM Books

MRS V3.4 Protocol Reference V2


Configuring and Monitoring BGP6

The BGP4 protocol with the addition of RFC 2283, Multiprotocol Extensions for BGP4 (BGP4+), supports IPv6 routing information.

This chapter describes the BGP6 configuring and monitoring commands and includes the following sections:


Accessing the BGP6 Configuration Environment

To access the BGP6 configuration environment, enter the following command at the Config> prompt:

  Config> protocol bgp6
  BGP6 Config>

BGP6 Configuration Commands

This section describes the BGP6 configuration commands. These commands allow you to modify the BGP6 protocol behavior to meet your specific requirements. Some amount of configuration is necessary to produce a fully functional BGP6 router. Enter BGP6 configuration commands at the BGP6 Config> prompt.

Table 122. BGP6 Configuration Command Summary
 Command   Function 
? (Help) Displays all the commands available for this command level or lists the options for specific commands (if available). See "Getting Help".
 Add   Add BGP6 neighbors and policies. 
 Attach   Attaches receive and send policy-list to a particular neighbor. 
 Change   Modifies information that was originally entered with the add command. 
 Delete   Deletes BGP6 configuration information that had been entered with the add command. 
 Disable   Disables certain BGP6 features that have been turned on by the enable command. 
 Enable   Enables BGP6 speakers, BGP6 neighbors. 
 List   Displays BGP6 configuration items. 
 Move   Changes the order in which policies and aggregates are defined. 
 Set   Sets the IPv6-route-table-scan-timer. 
 Update   Manipulates a policy in a configured policy-list name using the submenu add, delete, change and move commands. 
Exit Returns you to the previous command level. See "Exiting a Lower Level Environment".

Add

Use the add command to add BGP6 information to your configuration.

Syntax:

add
aggregate . . .
neighbor . . .
no-receive asnum . . .
originate-policy . . .
policy-list . . .
receive-policy . . .
send-policy. . .

aggregate network prefix Prefix Length
The add aggregate command causes the BGP6 speaker to aggregate a block of addresses, and advertise a single route to its BGP6 neighbors. You must specify the network prefix common to all the routes being aggregated and its prefix length. The following example illustrates how to aggregate a block of addresses.
  1. The network prefix specifies the addresses being affected. The prefix is the first address in a range of addresses specified in a BGP6 policy.
    Valid Values: a valid IPv6 unicast address or IPv4 compatible address, excluding the following:
    • link-local addresses (FE80::)
    • site-local addresses (FEC0::)
    • loopback address (::1)
    • IPv4 mapped IPv6 addresses (::FFFF:<IPv4 address>)
    Default Value: none
  2. The prefix length applies to the address specified in Network Prefix to generate an address used in a BGP6 policy.
    Valid Values: 8 - 128
    Default Value: 64

Example:
add aggregate
Network Prefix []? 2000::
Prefix Length [64]? 16

When you add an aggregate definition, remember to define a policy to block the aggregated routes from being exported. If you do not, the router will advertise both the individual routes and the aggregate you have defined. This does not apply when you are aggregating the routes, which are originated from it's IGP routing table.

neighbor neighbor address AS# init timer connect timer hold timer keep alive timer tcp segment size

Use the add neighbor command to define a BGP6 neighbor. The neighbor can be internal to the BGP6 speaker's AS, or external. To activate this neighbor dynamically use the reset neighbor command from BGP6 monitoring.

Neighbor address
The neighbor address is the IPv6 address of the neighbor you wish to peer with. It could be within your own autonomous system or in another autonomous system. If it is an external neighbor, both BGP6 speakers must share the same network. There is no such restriction for internal neighbors.
Valid Values: a valid IPv6 unicast address or IPv4 compatible address, excluding the following:
  • link-local addresses (FE80::)
  • site-local addresses (FEC0::)
  • loopback address (::1)
  • IPv4 mapped IPv6 addresses (::FFFF:<IPv4 address>)
  • zero address (::0)
Default Value: none

AS#
The AS# is your own autonomous system number for internal neighbor or neighbor's autonomous system number. The AS number of the neighbor has:
Valid Values: An integer in the range of 1 - 65535
Default Value: 1

Init timer
The init timer to specifies the amount of time the BGP6 speaker waits to initialize resources and reinitiate transport connection with the neighbor in case the speaker has previously changed to IDLE state due to an error. If the error persists, this timer increases exponentially.
Valid Values: 0 to 65535 seconds.
Default Value: 12 seconds

Connect timer
The connect timer specifies the amount of time the BGP6 speaker waits to reinitiate transport connection to its neighbor, if the TCP connection fails while in either CONNECT or ACTIVE state. In the mean time, the BGP6 speaker continues to listen for any connection that may be initiated by its neighbor.
Valid Values: 0 to 65535 seconds.
Default Value: 120 seconds

Hold timer
Enter the hold timer to specify the length of time the BGP6 speaker waits before assuming that the neighbor is unreachable. Both neighbors exchange the configured information in OPEN message and choose the smaller of the two timers as their negotiated Hold Timer value.

Once neighbors have established BGP6 connection, they exchange Keepalive messages at frequent intervals to ensure that the connection is still alive and the neighbors are reachable. The Keep-Alive timer interval is calculated to be one-third of the negotiated hold timer value. Hence the hold timer value must be either zero or at least three seconds.

Note that on switched lines, you may wish to use the Hold Timer value of zero to save bandwidth by not sending Keepalives at frequent intervals.

Valid Values: 0 to 65535 seconds.
Default Value: 90 seconds

TCP segment size
The TCP segment size specifies the maximum data size that may be exchanged on the TCP connection with a neighbor. This value is used for active TCP connection with the neighbor.
Valid Values: 1 to 65535 bytes.
Default Value: 1220 bytes

Example:
add neighbor
Neighbor address []? 2002:9::6205
AS [1]? 2002
Init timer [12]?
Connect timer [120]?
Hold timer [90]?
TCP segment size [1220]?

no-receive AS#
Use the add no-receive AS# to exclude AS-paths if the particular AS number appears anywhere inside the AS-path list.

The AS# has:

Valid Values: 1 to 65535
Default Value: 1

Example:
add no-receive
Enter AS: [1]? 2003

originate-policy (exclusive/ inclusive) network prefix Prefix Length address match (Exact/Range) tag

Use the add originate-policy command to specify the value to use in selecting routes for advertisement.

Exclusive
Exclusive policies prevent route information from being included in the BGP6 speaker's routing table.

Inclusive
Inclusive policies ensure that specific routes will be included in the BGP6 speaker's routing table.

Network prefix
This parameter specifies the network address affected by this policy.
Valid Values:a valid IPv6 unicast address or IPv4 compatible address, excluding the following:
  • link-local addresses (FE80::)
  • site-local addresses (FEC0::)
  • loopback address (::1)
  • IPv4 mapped IPv6 addresses (::FFFF:<IPv4 address>)
Default Value: none

Prefix length
The prefix length applies to the address specified in Network Prefix to generate an address used in a BGP6 policy.
Valid Values: 0 - 128
Default Value: 0

Address match
The address, or range of addresses, that will be affected by the policy statement.
Valid Values: Exact or Range
Default Value: Range

Tag
The tag value represents the AS number from which the route is learned. The tag value is used for interacting with an IGP, like RIP6. See "Set" for information on importing BGP6 routes and BGP6 autotag generation.
Valid Values: 0 - 65535
Default Value: 0

The following example includes all routes in the BGP6 speaker's IGP routing table to be advertised.

Example:
add originate-policy inclusive
Network Prefix [::]? 
Prefix length[0]? 
Address Match (Exact/Range) [Range]? 
Tag [0]?

policy-list
Use the add policy-list command to configure a group of policies, which can be attached to a specific neighbor using the attach policy-to-neighbor command.

Name
Specifies the name to be used to identify the group of policies.
Valid Values: A string of 1 - 15 ASCII characters
Default Value: None

Example: add policy-list

Name[]? nbr1-rcv
Policy Type(Receive/Send)[Receive]?Receive

Example: add policy-list

Name[]? nbr1-snd
Policy Type(Receive/Send)[Receive]?Send

receive-policy (exclusive/ inclusive) network prefix Prefix Length address match originating AS# adjacent AS# igpmetric (inclusive only)

Use the add receive-policy command to determine what routes will be imported to the BGP6 speaker's routing table.

Exclusive policies prevent route information from being included in the BGP6 speaker's routing table.

Inclusive policies ensure that specific routes will be included in the BGP6 speaker's routing table.

Network prefix
Specifies the addresses being affected.
Valid Values: a valid IPv6 unicast address or IPv4 compatible address, excluding the following:
  • link-local addresses (FE80::)
  • site-local addresses (FEC0::)
  • loopback address (::1)
  • IPv4 mapped IPv6 addresses (::FFFF:<IPv4 address>)
Default Value: none

Prefix Length
The prefix length applies to the address specified in network prefix to generate an address used in a BGP6 policy.

Valid Values: 0 - 128
Default Value: 0

Address match
The address match is a range of addresses or an exact address.
Valid Values: Exact or Range
Default Value: Range

Originating AS#
An originating AS# has:
Valid Values: 0 to 65535
Default Value: 0

Adjacent AS#
The adjacent AS# specifies the neighboring AS number.
Valid Values: 0 to 65535
Default Value: 0

IGP metric
The IGP metric(for inclusive receive-policies only) specifies the metric value with which the accepted routes are imported into the speaker's IGP routing table. If the IGP metric is -1, these routes will not be imported into the IGP; thus, these routes are not re-advertiseable.
Valid Values: -1 to 65535
Default Value: 0
Example:
add receive-policy exclusive
Network Prefix [::]? 2003::
Prefix length[0]? 16
Address Match (Exact/Range) [Range]?
Originating AS# [0]? 168
Adjacent AS# [0]? 165

Example:
add receive-policy inclusive
Network Prefix [::]? 2000:: Prefix Length [0]? 64 
Address Match (Exact/Range) [Range]?
Originating AS# [0]?
Adjacent AS# [0]?
IGP-metric [0]?

send-policy (exclusive/ inclusive) network prefix Prefix Length address match tag adjacent AS#

Use the add send-policy command to create policies that determine which of the BGP6 speaker's learned routes will be readvertised. These routes could be internal or external to the BGP6 speaker's AS.

Exclusive policies prevent route information in the BGP6 speaker's routing table from being advertised to BGP6 neighbors.

Inclusive policies ensure that specific routes in the BGP6 speaker's routing table will be advertised to BGP6 neighbors.

Network prefix
The network prefix is for the addresses being affected.
Valid Values: a valid IPv6 unicast address or IPv4 compatible address, excluding the following:
  • link-local addresses (FE80::)
  • site-local addresses (FEC0::)
  • loopback address (::1)
  • IPv4 mapped IPv6 addresses (::FFFF:<IPv4 address>)
Default Value: none

Prefix length
The prefix length applies to the address specified in Network Prefix to generate an address used in a BGP6 policy.
Valid Values: 0 - 128
Default Value: 0

Address match
The Address match is a range of addresses or an exact address.
Valid Values: Exact or Range
Default Value: Range

Tag
The tag value represents the AS number from which the route is learned. The tag value is used for interacting with an IGP, like RIP6. See "Set" for information on importing BGP6 routes and BGP6 autotag generation.
Valid Values: 0 to 65535
Default Value: 0

Adjacent AS#
The adjacent AS# specifies the neighboring AS number.
Valid Values: 0 to 65535
Default Value: 0
Example:
add send exclusive
Network Prefix []? 2003::
Prefix length[0]? 16
Address Match (Exact/Range) [Range]? 
Tag [0]?
Adjacent AS# [0]? 

Attach

Use the attach policy-to-neighbor command to attach a configured policy-list name to a specific neighbor. You can attach up to three receive and three send policy-list names.

Syntax:

attach
policy-to-neighbor

Example: attach policy-to-neighbor

Neighbor address [::]? 2003::
First receive policy list name (none for global AS based policy)[]? nbr1-rcv
Second receive policy list name (none for exit)[]? 
First send policy list name (none for global AS based policy)[]? nbr1-snd
Second send policy list name (none for exit)[]?
 

Change

Use the change command to change a BGP6 configuration item previously installed by the add command.

Syntax:

change
aggregate . . .

neighbor . . .

originate-policy . . .

policy-to-neighbor

receive-policy . . .

send-policy. . .

aggregate index# network prefix Prefix Length
This example changes the current aggregate (aggregate 1).
Example:
change aggregate 1
Network Prefix [2000::]? 2001::
Prefix Length [16]? 

neighbor neighbor IPv6 address AS# init timer connect timer hold timer keep alive timer tcp segment size
Use this command to change the configuration parameter values for an existing neighbor. This command may not be used to change the address for an existing neighbor.

To reactivate the neighbor dynamically use the reset neighbor command from BGP6 monitoring.

The neighbor address to be modified has:

Valid Values: Any currently configured neighbor address
Default Value: none

The following example changes the value of the hold timer to zero for neighbor 2002:0::6205.

Example:
change neighbor 2002:0::6205
AS [2002]?
Init timer [12]?
Connect timer [60]?
Hold timer [12]? 0
TCP segment size [1220]?

originate-policy index# (exclusive/ inclusive) network prefix Prefix Length address match tag
Use the change originate-policy command to alter an existing originate policy definition.

This example alters the BGP6 speaker's originate policy.

Example:
change originate-policy
Enter index of originate-policy to be modified [1]?
Policy Type (Inclusive/Exclusive) [Exclusive]? inclusive
Network Prefix [2003::]? 2004::
Prefix Length [16]? 16
Address Match (Exact/Range) [Range]?
Tag [0]?

policy-to-neighbor
Use the change policy-to-neighbor command to change a policy-list attachment to a particular neighbor.
Example:
change policy-to-neighbor
Neighbor address [0::0]? 2003::
First receive policy list name to be changed[nbr1-rcv]? 
Second receive policy list name to be changed[]?
Third receive policy list name to be changed[]?
First send policy list name to be changed[nbr1-snd]? 
Second send policy list name to be changed[]?
Third send policy list name to be changed[]?

receive-policy index# (exclusive/inclusive) network prefix Prefix Length address match originating AS# adjacent AS# igpmetric (inclusive only)
Use the change receive-policy command to alter an existing receive policy definition.

This example adds a restriction to the BGP6 speaker's receive-policy. Rather than import route information from every BGP6 peer into its IGP routing table, it will now prevent routes from AS 165 from being imported.

Example:
change receive-policy
Enter index of receive-policy to be modified [1]?
Policy Type (Inclusive/Exclusive) [Inclusive]? exclusive
Network Prefix [2003::]?
Prefix Length [16]?
Address Match (Exact/Range) [Range]?
Originating AS# [0]?
Adjacent AS# [0]? 165

send-policy index# (exclusive/ inclusive) network prefix Prefix Length address match tag adjacent AS#
Use the change send-policy command to alter an existing send policy to one that is more inclusive, or more exclusive.

This example adds a restriction to the BGP6 speaker's send policy.

Example:
change send-policy
Enter index of send-policy to be modified [1]?
Policy Type (Inclusive/Exclusive) [Inclusive]? exclusive
Network Prefix [0::0]? 2004:6::6205
Prefix Length [16]? 16
Address Match (Exact/Range) [Range]?
Tag [0]?
Adjacent AS# [0]? 165

Delete

Use the delete command to delete a BGP6 configuration item previously installed by the add command.

Syntax:

delete
aggregate . . .

neighbor . . .

no-receive . . .

originate-policy . . .

policy-list . . .

policy-to-neighbor

receive-policy . . .

send-policy. . .

aggregate index#
You must specify the index number of the aggregate you want to delete.

Example: delete aggregate 1

neighbor neighbor IPv6 address
Use this command to delete a BGP6 neighbor. You must specify the neighbor's network address.

The neighbor's network address to be deleted has:

Valid Values: Any currently configured neighbor address
Default Value: none

To deactivate this neighbor dynamically use the reset neighbor command from BGP6 monitoring.

Example: delete neighbor 2002:9::6024

no-receive AS#
Use this command to delete the no-receive policy set up for a particular AS. You must specify the AS number.

The AS# has:

Valid Values: 1 to 65535
Default Value: none

Example: delete no-receive 168

originate-policy index#
Use this command to delete a specific originate policy. You must specify the index number associated with the policy.

Example: delete originate-policy 2

policy-list
Use the delete policy-list command to delete a policy-list.

Example: delete policy-list

Name of policy-list to delete []? nbr1-rcv
All policies defined for 'nbr1-rcv' will be deleted.
Are you sure you want to delete (Yes or [No]? Yes
Policy-list 'nbr1-rcv' is deleted. 

The policy-to-neighbor attachment will be adjusted accordingly.

policy-to-neighbor
Use the delete policy-to-neighbor command to delete an existing policy-list name attachment to a particular neighbor.

Example: delete policy-to-neighbor

Neighbor address []? 2009:9::6205
Remove first receive policy-list name [nbr1-rcv]
Are you sure you want to remove (Yes or [No])? yes
Remove first send policy-list name [nbr1-snd]
Are you sure you want to remove (Yes or [No])? yes   

receive-policy index#
Use this command to delete a specific receive policy. You must specify the index number associated with the policy.

Example: delete receive-policy

Enter index of receive-policy to be deleted [1]?

send-policy index#
Use this command to delete a specific send policy. You must specify the index number associated with the policy.

Example: delete send-policy 4

Disable

Use the disable command to disable a previously enabled BGP6 neighbor or speaker. Note that neighbors are implicitly enabled whenever added with the add command.

Syntax:

disable
BGP6 speaker

compare-med-from-diff-AS

neighbor . . .

BGP6 speaker
Use the disable BGP6 speaker command to disable the BGP6 protocol.

Example: disable BGP6 speaker

compare-med-from-diff-AS
Use this command to disable a MED comparison between different ASs.

Example: disable compare-med-from-diff-AS

neighbor neighbor IPv6 address
Use this command to disable a currently configured neighbor. The neighbor address has:

Valid Values: Any valid IPv6 address
Default Value: none

Example: disable neighbor 2002:9::6205

Enable

Use the enable command to activate the BGP6 features, capabilities, and information added to your BGP6 configuration.

Syntax:

enable
BGP6 speaker

compare-med-from-diff-AS

neighbor . . .

BGP6 speaker AS# tcp segment size
Use the enable BGP6 speaker command to enable the BGP6 protocol.

  1. The AS# is associated with this collection of routers and nodes.
    Valid Values: 1 to 65535
    Default Value: 1
  2. Enter the TCP segment size to specify the maximum segment size that BGP6 should use for passive TCP connections.
    Valid Values: 1 to 65535 bytes.
    Default Value: 1220 bytes
Example:
enable BGP6 speaker
AS [0]? 165
TCP segment size [1220]?

compare-med-from-diff-AS
Use this command to enable MED comparison between different ASs.

Example: enable compare-med-from-diff-AS

neighbor neighbor IPv6 address
Use this command to enable a BGP6 neighbor.

The neighbor address has:

Valid Values: Any currently configured neighbor address
Default Value: none

Example: enable neighbor 2002:9::6205

List

Use the list command to display various pieces of the BGP6 configuration data, depending on the particular subcommand invoked.

Syntax:

list
aggregate

all

BGP6 speaker

neighbor

no-receive

originate-policy

policy-list . . .

policy-to-neighbor

receive-policy

send-policy

aggregate
Use the list aggregate command to all aggregated routes defined with the add aggregate command.

Example: list aggregate

Aggregation:
Index    Prefix/Prefix length
1        2000::/16

all
Use the list all command to list the BGP6 neighbors, policies, aggregated routes, and no-receive-as records in the current BGP6 configuration.

Example: list all

 
                BGP6 Protocol:          Enabled
                AS:                    710
                TCP-Segment Size:      1220
 
Neighbors and their AS:
                                                      Init  Conn  Hold  TCPSEG
Address                                  State  AS    Timer Timer Timer Size
2003:7:8:2::820                          ENABLD 820   12    120   90    1220
 
2002:9::6205                             ENABLD 2002  12    120   90    1220
 
 
Receive-Policies:
Index Type Prefix/Prefix length                        Match OrgAS AdjAS IGPmet
1     INCL ::/0                                        Range 0     0     0
   
2     EXCL 2003::/16                                   Range 0     0    
 
Send-Policies:
Index  Type  Prefix/Prefix length                        Match Tag   AdjAS
1      INCL  ::/0                                        Range 0     0   
 
2      EXCL  2003::/16                                   Range 0     0   
 
 
Originate-Policies:
Index  Type  Prefix/Prefix Length                        Match  Tag
1      INCL  ::/0                                        Range  0    
2      EXCL  2003::/16                                   Range  0    
 
Aggregation:
Index  Prefix/Prefix Length                       
1      2000::/16                                  
 
AS-PATH with following ASs will be discarded:
AS 2003
compare-med-from-diff-as is enabled.
IPv6-route-table-scan-timer value is 2 seconds.

BGP6 speaker
Use the list BGP6 speaker command to derive information on the BGP6 speaker. The information provided is as follows:
Example:
list BGP6 speaker
BGP6 Protocol:          Enabled
AS:                     165
TCP-Segment Size:       1220

neighbor
Use the list neighbor command to derive information on BGP6 neighbors.

Example: list neighbor

Neighbors and their AS along with attached policy-list name(s):
                                                      Init  Conn  Hold  TCPSEG
Address                                  State  AS    Timer Timer Timer Size
2003:7:8:2::820                          ENABLD 820   12    120   90    1220
 
2002:9::6205                             ENABLD 2002  12    120   90    1220
 

no-receive
Use the list no-receive command to derive information on no-receive-AS definitions that have been added to the BGP6 configuration.

Example: list no-receive

AS-PATH with following autonomous systems will be discarded:
AS  178
AS  165

originate-policy all index prefix
Use the list originate-policy command to derive information on the originate policies that have been added to the BGP6 configuration.

Example: list originate-policy

Originate-Policies:
Index  Type  Prefix/Prefix Length                        Match  Tag
1      INCL  ::/0                                        Range  0    
2      EXCL  2003::/16                                   Range  0

policy-list
Use the list policy-list command to list configured policy-list names.

Example: list policy-list

BGP6 Config>li policy list
Policy list:
nbr1-rcv  Receive
nbr1-snd  Send

policy-to-neighbor
Use the list policy-to-neighbor command to list policies attached to neighbors.

Example: list policy-to-neighbor

Neighbor address                          Receive          Send
2002:9::6205                              rec1             send1

receive-policy adj-as-number all or index or prefix
Use the list receive-policy command to derive information on the receive policies that have been added to the BGP6 configuration. You can display all receive policies defined for an AS, or display policies by index or prefix number.

Example: list receive-policy

Receive-Policies:
Index Type Prefix/Prefix length                        Match OrgAS AdjAS IGPmet
1     INCL ::/0                                        Range 0     0     0
   
2     EXCL 2003::/16                                   Range 0     0    

send-policy adj-as-number all or index or prefix
Use the list send-policy command to display information on send policies defined for specified autonomous systems. You can display all send policies defined for an AS, or display policies by index or prefix number.

Example: list send-policy

Send-Policies:
Index  Type  Prefix/Prefix length                        Match Tag   AdjAS
1      INCL  ::/0                                        Range 0     0   
 
2      EXCL  2003::/16                                   Range 0     0    

Move

Use the move command to change the order in which policies and aggregates have been defined. This changes the order in which the router applies existing policies to route information. Before using this command, it is advisable to use the list command to see what policies have been defined.

Syntax:

move
aggregate or originate-policy or receive-policy or send-policy

Example:

move originate-policy
Enter index of originate-policy to move [1]? 3
Move record AFTER record number [0]?

Set

Use the set command to set the IPv6-route-table-scan-timer. The IPv6-route-table-scan-timer value is used to set the IPv6 forwarding table scanning time interval for BGP6 updates.

Syntax:

set
ipv6-route-table-scan-timer
Valid Values: 1 to 10
Default Value: 1
Example:
set ipv6-route-table-scan-timer
Timer Value in seconds [1]? 2   

Update

Use the update command and sub-commands to manipulate policies.

Syntax:

update
policy-list

Receive Policy Example:

update policy-list
Name[]? nbr1-rcv
    

Add

Use the Add command to add receive or send policies within the update command.

Example: Adding a receive policy

BGP6 Config>add POLICY-LIST
Policy-list name []? rec1
Policy Type (Receive/Send) [Receive]? 
BGP6 Config>UPDATE POLICY-LIST
Policy-list name []? rec1
Policy-list rec1:Receive Config>add
Policy Type (Inclusive/Exclusive) [Exclusive]? 
Network Prefix [::]? 1234::
Prefix Length [0]? 16
Address Match (Exact/Range) [Range]? 
Originating AS# [0]? 
Any AS# [0]? 
Policy-list rec1:Receive Config>list
Receive Policy list for rec1:
Idx T Prefix/Length/Match                          OrgAS AnyAS MED   Weight
LP    IGPm
1   E 1234::/16/R                                  0     0     
 
Policy-list rec1:Receive Config>add
Policy Type (Inclusive/Exclusive) [Exclusive]? inc
Network Prefix [::]? 5678::
Prefix Length [0]? 16
Address Match (Exact/Range) [Range]? 
Originating AS# [0]? 
Any AS# [0]? 
MED [0]? 
Local-pref [0]? 
Weight [0]? 
IGP-metric [0]? 
Policy-list rec1:Receive Config>list
Receive Policy list for rec1:
Idx T Prefix/Length/Match                          OrgAS AnyAS MED   Weight
LP    IGPm
1   E 1234::/16/R                                  0     0     
2   I 5678::/16/R                                  0     0     0     0   
 

Example: Adding a send policy

BGP6 Config>add POLICY-LIST 
Policy-list name []? send1 
Policy Type (Receive/Send)
[Receive]?  send
BGP6 Config>UPDATE POLICY-LIST 
Policy-list name []? send1
Policy-list send1:Send Config>add
Policy Type (Inclusive/Exclusive) [Exclusive]? i
Network Prefix [::]? 1234::
Prefix Length [0]? 16
Address Match (Exact/Range) [Range]? 
Originating AS# [0]? 
Any AS# [0]? 
Tag [0]? 
MED [0]? 
# of AS padding [0]? 
Policy-list send1:Send Config>list
Send Policy list for send1:
Idx T Prefix/Length/Match                          OrgAS AnyAS Tag   MED 
 ASpad
1   I 1234::/16/R                                  0     0     0     0   
 

Notes:

  1. There will be no prompting for MED, Local-pref, Weight, and IGP-metric parameters for exclusive receive policy. MED, Local-pref values will be used from received advertisement if they are configured as value '0'. The value '0' for the Weight parameter indicates to ignore the weight value in the route selection process.

  2. Prompting for MED and # of AS padding parameter values occurs only for inclusive send policies.

Change

Use the Change command to change policies within the update command.

Example:

Enter index of receive-policy to be modified [1]?

Delete

Use the delete command to delete policies within the update command.

Example:

Enter index of receive-policy to be deleted [1]?

Move

Use the move command to move policies within the update command.

Example:

Enter index of receive-policy to move [1]?
Move record after record number [0]?

List

Use the list policy-list command to list receive policies within the update command.

Example: list policy-list

Receive Policy list for rec1:
Idx T Prefix/Length/Match                          OrgAS AnyAS MED   Weight
LP    IGPm
1   E 1234::/16/R                                  0     0     
2   I 5678::/16/R                                  0     0     0     0   
 

Send Policy Example:

update policy-list
Name[]? nbr1-rcv
    

Accessing the BGP6 Monitoring Environment

To access the BGP6 monitoring environment, enter the following command at the + prompt:

  + protocol bgp6
  BGP6>

BGP6 Monitoring Commands

This section describes the BGP6 monitoring commands. These commands allow you to modify the BGP6 protocol behavior to meet your specific requirements. Some amount of configuration is necessary to produce a fully functional BGP6 router. Enter BGP6 monitoring commands at the BGP6> monitoring prompt.

Table 123. BGP6 Monitoring Command Summary
 Command   Function 
? (Help) Displays all the commands available for this command level or lists the options for specific commands (if available). See "Getting Help".
 Disable neighbor   Disables a particular neighbor or all neighbors. 
 Dump routing tables   Lists the contents of the IPv6 routing table. 
 List   Lists all BGP routing table entries. 
 Enable neighbor   Enables a particular neighbor or all neighbors. 
 Neighbors   Displays currently active neighbors. 
 Parameter   Displays installed BGP6 globals in the BGP6 system. 
 Paths   Displays all available paths in the database. 
 Ping6   Sends ICMP Echo Requests to another host once a second and watch for a response. This command can be used to isolate trouble in an internetwork environment. 
 Policy-list   Displays the current installed policy for specific neighbor and usage statics of each policy. 
 Reset neighbor   Resets a particular neighbor. 
 Traceroute6   Displays the complete path (hop-by-hop) to a particular destination. 
Exit Returns you to the previous command level. See "Exiting a Lower Level Environment".

Disable Neighbor

Use the disable neighbor command to disable a particular neighbor or all neighbors that have been enabled. This command brings down the BGP6 session and removes the routes learned from that neighbor.

Syntax:

disable neighbor IPv6 neighbor address

Example:
disable neighbor
Enter a Neighbor address or :: for all neighbors []? ::
neighbor 2003:1::6105 disabled

Dump Routing Tables

For a complete explanation of the dump routing tables command, refer to the Dump Routing Tables command on page Dump routing tables.

Example:

Type   Dest net/Prefix                              Cost Age  Next hop(s)/Net
 
BGPR   2001:6::/64                                  0     193  IP64/0    
BGPR   2001:7::/64                                  0     187  IP64/0    
BGPR   2001:9::/64                                  0     200  IP64/0    
BGPR   2001:17::/64                                 0     200  IP64/0    
 Dir*  2002:2::/64                                  1     7889 Eth/1     
RIP6   2002:5::/64                                  3     10   FE80::220:35FF:FE45:2488
 Eth/1
RIP6   2002:6::/64                                  2     10   FE80::220:35FF:FE45:2488
 Eth/1 
RIP6   2002:9::/64                                  2     10   FE80::220:35FF:FE45:2488
 Eth/1
RIP6   2002:99::/64                                 3     10   FE80::220:35FF:FE45:2488
 Eth/1
RIP6   2002:1111::/64                               3     10   FE80::220:35FF:FE45:2488
 Eth/1
 Dir*  2003:1::/64                                  1     7889 IP64/0
 
IPV6 Routing table size: 768 nets (79872 bytes), 11 nets known
                      0 nets hidden, 0 nets deleted, 1 nets inactive
                      0 routes used internally, 756 routes free

Enable Neighbor

Use the enable neighbor command to enable a particular neighbor or enable all neighbors that have been disabled. This command starts the BGP6 session with neighbor.

Syntax:

enable neighbor
IPv6 neighbor address

Example:

Enter a Neighbor address or :: for all neighbors []? ::
neighbor 2003:1::6105 enabled

List

Use the list command to dump all BGP6 routing table entries, or to display information on routes advertised to, or received from, specified BGP6 neighbor addresses (destinations).

Syntax:

list
all
dst_network network address
rt_rcved_from_nbr network address
rt_sent_to_nbr network address

all

Example:

BGP6> list all
 
MED   Weight LPref AAG AGRAS ORG AS-Path
 
0     0      0     No  0     IGP seq[2001]
Network/Prefixlen: 2001:6::/64
Next Hop:          2003:1::6105
Next Hop LLA:      FE80::3030:30FF:FE30:B
 
0     0      0     No  0     IGP seq[2001]
Network/Prefixlen: 2001:7::/64
Next Hop:          2003:1::6105
Next Hop LLA:      FE80::3030:30FF:FE30:B
 
0     0      0     No  0     IGP seq[2001]
Network/Prefixlen: 2001:9::/64
Next Hop:          2003:1::6105
Next Hop LLA:      FE80::3030:30FF:FE30:B
 
0     0      0     No  0     IGP seq[2001]
Network/Prefixlen: 2001:17::/64
Next Hop:          2003:1::6105
Next Hop LLA:      FE80::3030:30FF:FE30:B
 
0     0      0     No  0     IGP
Network/Prefixlen: 2002:2::/64
Next Hop:          2002:2::6202
Next Hop LLA:      ::
 
0     0      0     No  0     IGP
Network/Prefixlen: 2002:5::/64
Next Hop:          2002:2::6202
Next Hop LLA:      ::
 
0     0      0     No  0     IGP
Network/Prefixlen: 2002:6::/64
Next Hop:          2002:2::6202
Next Hop LLA:      ::
 
0     0      0     No  0     IGP
Network/Prefixlen: 2002:9::/64
Next Hop:          2002:2::6202
Next Hop LLA:      ::
 
0     0      0     No  0     IGP
Network/Prefixlen: 2002:99::/64
Next Hop:          2002:2::6202
Next Hop LLA:      ::
 
0     0      0     No  0     IGP
Network/Prefixlen: 2002:1111::/64
Next Hop:          2002:2::6202
Next Hop LLA:      ::
 
 

dst_network net address
Displays detailed information on the specified route or destination network. The command shows how a specific route was learned, the best path to a specific destination, the metric associated with the route, and other information.

Example:

BGP6>list dst_network
Destination network prefix []? 2002:1111::
Do you want specify prefix len? [No]: y
Prefix len (0-128) [64]? 
 
Destination: 2002:1111::/64
             Age:30, Upd#:4, LastSent: 0002:10:17
 
Eligible paths: 1
PathID: 0 - (Best Path)
        ASpath:
        Origin: IGP, Pref: 0, LocalPref: 0
        Metric: 0, Weight: 0, MED: 0
        NextHop:     2002:2::6202                            
        NextHop LLA: ::                                      
        Neighbor:    2002:2::6202                            
        AtomicAggr: No

ASpath
Enumeration of autonomous systems along the path.

-seq:
Sequence of autonomous systems in order in the path

-set:
Set of autonomous systems in the path.

Origin
The originator of the destination. This is EGP, IGP, or Incomplete (originated by some other means not known).

LocalPref
The originating router's degree of preference for the destination.

Metric
The path metric with which the route is imported.

Weight
The path weight.

MED
A multi-exit discriminator value, used to discriminate among multiple entry/exit points to the same AS.

NextHop
The address of the router to use as the forwarding address for destinations reachable via the given path.

AtomicAggr
Indicates whether the router advertising the path has included the path in an atomic-aggregate.

rt_rcved_from_nbr net address
Lists all routes received from the specified BGP neighbor.

Example:

BGP6>list rt_rcved_from_nbr
BGP6 neighbor address []? 2003:1::6105
 
        Destinations obtained from BGP6 neighbor 2003:1::6105
 
MED   Weight LPref AAG AGRAS ORG AS-Path
 
0     0      0     No  0     IGP seq[2001]
Network/Prefixlen: 2001:9::/64
Next Hop:          2003:1::6105
Next Hop LLA:      FE80::3030:30FF:FE30:B
 
0     0      0     No  0     IGP seq[2001]
Network/Prefixlen: 2001:7::/64
Next Hop:          2003:1::6105
Next Hop LLA:      FE80::3030:30FF:FE30:B
 
0     0      0     No  0     IGP seq[2001]
Network/Prefixlen: 2001:17::/64
Next Hop:          2003:1::6105
Next Hop LLA:      FE80::3030:30FF:FE30:B
 
0     0      0     No  0     IGP seq[2001]
Network/Prefixlen: 2001:6::/64
Next Hop:          2003:1::6105
Next Hop LLA:      FE80::3030:30FF:FE30:B

rt_sent_to_nbr net address
Lists all routes advertised to the specified BGP neighbor.

Example:

BGP6>list rt_sent_to_nbr
BGP6 neighbor address []? 2003:1::6105
 
        Destinations advertised to BGP6 neighbor 2003:1::6105
 
MED   Weight LPref AAG AGRAS ORG AS-Path
 
0     0      0     No  0     IGP
Network/Prefixlen: 2002:9::/64
Next Hop:          2002:2::6202
Next Hop LLA:      ::
 
0     0      0     No  0     IGP
Network/Prefixlen: 2002:5::/64
Next Hop:          2002:2::6202
Next Hop LLA:      ::
 
0     0      0     No  0     IGP
Network/Prefixlen: 2002:99::/64
Next Hop:          2002:2::6202
Next Hop LLA:      ::
 
0     0      0     No  0     IGP
Network/Prefixlen: 2002:1111::/64
Next Hop:          2002:2::6202
Next Hop LLA:      ::
 
0     0      0     No  0     IGP
Network/Prefixlen: 2002:6::/64
Next Hop:          2002:2::6202
Next Hop LLA:      ::

Neighbors

Use the neighbors command to display information on all active BGP6 neighbors.

Syntax:

neighbors
IPv6 neighbor address

Example:

BGP6>neighbors
 
                                     Status State       DAY-HH:MM:SS   AS   Upd#
Address: 2003:1::6105                            
bgp6-ID: 20.1.7.5                    ENABLD Established 000-00:03:42   2001 11       

IPv6-Address
Specifies the IPv6 address of the BGP6 neighbor.

State
Specifies the state of the connection. Possible states are:

Connect
Waiting for the TCP connection to the neighbor to be completed.

Active
In the event of TCP connection failure, the state is changed to Active, and the attempt to acquire the neighbor continues.

OpenSent
In this state OPEN has been sent, and BGP6 waits for an OPEN message from the neighbor.

OpenConfirm
In this state a KEEPALIVE has been sent in response to neighbor's OPEN, and waits for a KEEPALIVE/NOTIFICATION from the neighbor.

Established
A BGP6 connection has been successfully established, and can now start to exchange UPDATE messages.

BGP-ID
Specifies the neighbor's BGP6 Identification number.

AS
Specifies the neighbor's AS number.

Upd#
Specifies the sequence number of the last UPDATE message sent to the neighbor.

IPv6 neighbor address
Use the neighbor command to display detailed data on a particular BGP6 neighbor.

Example:

BGP6>neighbors 2000::662:0
Active Conn: None
Passve Conn: Sprt:179   Dprt:1026  State: Established KeepAlive/Hold Time: 30/90
TCP connection errors: 1          TCP state transitions: 1         
 
BGP6 Messages:    Sent       Received                     Sent       Received
Open:             2          2          Update:           2          2         
Notification:     1          0          KeepAlive:        2          2         
Total Messages:   7          6         
 
Msg Header Errs:  Sent       Received                     Sent       Received
Conn sync err:    0          0          Bad msg length:   0          0         
Bad msg type:     0          0         
 
Open Msg Errs:    Sent       Received                     Sent       Received
Unsupp versions:  0          0          Unsupp auth code: 0          0         
Bad peer AS ident:0          0          Auth failure:     0          0         
Bad BGP ident:    0          0          Bad hold time:    0          0         
 
Update Msg Errs:  Sent       Received                     Sent       Received
Bad attr list:    0          0          AS routing loop:  0          0         
Bad wlkn attr:    0          0          Bad NEXT_HOP atr: 0          0         
Mssng wlkn attr:  0          0          Optional atr err: 0          0         
Attr flags err:   0          0          Bad netwrk field: 0          0         
Attr length err:  0          0          Bad AS_PATH attr: 0          0         
Bad ORIGIN attr:  0          0         
 
Total Errors:     Sent       Received                     Sent       Received
Msg Header Errs:  0          0          Hold Timer Exprd: 0          0         
Open Msg Errs:    0          0          FSM Errs:         0          0         
Update Msg Errs:  0          0          Cease:            1          0          

Parameter

Use the BGP6 parameter command to display installed BGP6 globals in the BGP6 system.

Syntax:

parameter

Example:

compare-med-from-diff-as is disabled.
IPv6-route-table-scan-timer value is 1 seconds.

Paths

Use the BGP6 paths command to display the paths stored in the path description data base.

Syntax:

paths

Example:

paths
PathId MED   AAG AGRAS RefCnt ORG AS_PATH
 
0      0     No  0     6      IGP
Next Hop:     2002:2::6202
Next Hop LLA: ::
 
1      0     No  0     2      IGP seq[2001]
Next Hop:     2003:1::6105
Next Hop LLA: FE80::3030:30FF:FE30:B
 
2      0     No  0     2      IGP seq[2001]
Next Hop:     2003:1::6105
Next Hop LLA: FE80::3030:30FF:FE30:B

PathId
Path identifier

NextHop
The address of the router to use as the forwarding address for the destinations that can be reached via the given path.

MED
The multi-exit discriminator used to discriminate among multiple entry/exit points to the same AS.

AAG
Indicates if the path has been atomic-aggregated that is the router that is advertising the given path has selected less specific route over the more specific one when presented with overlapping routes.

AGRAS
Indicates the AS number of the BGP6 speaker that aggregated the routes.

RefCnt
Indicates the number of path entities referring to the descriptor.

ORG
Specifies the originator of the advertised destinations in the given path: either EGP, IGP, or Incomplete (originated by some other means not known).

AS Path
Enumeration of autonomous systems along the path.

seq:
Sequence of autonomous systems in order in the path.

set:
Set of autonomous systems in the path.

Ping6

For an explanation of the ping6 command, see Ping6.

Policy-List

Use the policy-list command to display the current installed policy for specific neighbor and usage statistics of each policy.

Example:

BGP6>policy-list
Destination network prefix []? 2003:1::6105
Policy Type (Receive/Send/Origin) [All]? 
 
Receive policy list for all neighbors:
Idx T Match OrgAS AdjAS IGPmet Usage  Prefix 
1   I Range 0     0     0      5      2001::/16
 
AS-PATH with following ASs will be discarded:
 
 
Send policy list for all neighbor:
Idx T Match TAG   AdjAS Usage  Prefix  
1   I Range 0     0     11     2002::/16
 
Origin policy list for all neighbor:
Idx T Match Tag   Usage  Prefix
1   I Range 0     6      2002::/16 
BGP6>policy-list
Neighbor address []? 2000::1
Policy Type (Receive/Send/Origin) [All]? r
 
Receive policy list for neighbor '2000::1' :
Idx T Match OrgAS AnyAS MED   Weight LPref IGPmet Usage  Prefix 
1   I Range 0     0     10    0      100   0      0      ::/0
 
BGP6>policy-list
Neighbor address []? 2000::1
Policy Type (Receive/Send/Origin) [All]? s
 
Send policy list for neighbor '2000::1' :
Idx T Match OrgAS AnyAS Tag   MED   ASpad Usage  Prefix            
1   I Range 0     0     0     30    0     0      ::/0
 
BGP6>policy-list
Neighbor address []? 2000::1
Policy Type (Receive/Send/Origin) [All]? o
 
Origin policy list for all neighbor:
Idx T Match Tag   Usage  Prefix
1   I Range 0     2      ::/0 

Reset Neighbor

Use the reset neighbor command to reset the specified BGP6 neighbor, based on the neighbor configuration parameters stored in the configuration memory.

Syntax:

reset neighbor IPv6 neighbor address

Example:
reset neighbor
Enter a Neighbor address:  []? 2003:1::6105
resetting neighbor 2003:1::6105 

Sizes

Use the BGP6 sizes command to display the number of entries stored in the various data bases.

Syntax:

sizes

Example:
sizes
 
        # Paths:                                 10
        # Path descriptors:                      3
          Update sequence#:                      11
        # Routing tbl entries (allocated):       10
        # Current tbl entries (not imported):    0
        # Current tbl entries (imported to IGP): 4

Paths
Total number of eligible paths for all the routes in the BGP6 routing table.

Path descriptors
Total number of path descriptors in the database used to hold common path information.

Update sequence#
Indicates the current update sequence number.

Routing tbl entries (allocated)
Indicates the number of entries in BGP6 routing table.

Current tbl entries (not imported)
Indicates the number of BGP6 routes not imported into IGP.

Current tbl entries(imported to IGP)
Indicates the number of BGP6 routes imported into IGP.

Traceroute6

For an explanation of the traceroute6 command, see Traceroute6.


BGP6 Dynamic Reconfiguration Support

This section describes dynamic reconfiguration (DR) as it affects Talk 6 and Talk 5 commands.

CONFIG (Talk 6) Delete Interface

Border Gateway Protocol for IPv6 (BGP6) supports the CONFIG (Talk 6) delete interface command with the following consideration:

Deletes configured BGP6 external neighbors if the neighbor address has a common IPv6 prefix with an IPv6 address deleted on that interface.

GWCON (Talk 5) Activate Interface

The GWCON (Talk 5) activate interface command is not applicable for BGP6. BGP6 has no SRAM records associated with an interface.

GWCON (Talk 5) Reset Interface

The GWCON (Talk 5) reset interface command is not applicable for BGP6. BGP6 has no SRAM records associated with an interface.

GWCON (Talk 5) Component Reset Commands

BGP6 supports the following BGP6-specific GWCON (Talk 5) reset commands:

GWCON, Protocol Bgp6, Reset Neighbor Command

Description:
Adds or deletes a BGP6 neighbor. Changes neighbor parameters & policies.

Network Effect:
BGP6 neighbor connection and learned routes are updated based on configuration change.

Limitations:
None.

The following table summarizes the BGP6 configuration changes that are activated when the GWCON, protocol bgp6, reset neighbor command is invoked:
Commands whose changes are activated by the GWCON, protocol bgp6, reset neighbor command
CONFIG, protocol BGP6, add neighbor
CONFIG, protocol BGP6, change neighbor
CONFIG, protocol BGP6, delete neighbor
CONFIG, protocol BGP6, attach policy-to-neighbor
CONFIG, protocol BGP6, change policy-to-neighbor
CONFIG, protocol BGP6, delete policy-to-neighbor
CONFIG, protocol BGP6, add policy-list
CONFIG, protocol BGP6, update policy-list

GWCON (Talk 5) Temporary Change Commands

BGP6 supports the following GWCON commands that temporarily change the operational state of the device. These changes are lost whenever the device is reloaded, restarted, or you execute any dynamically reconfigurable command.
Commands
GWCON, protocol BGP6, enable neighbor
GWCON, protocol BGP6, disable neighbor

Non-Dynamically Reconfigurable Commands

The following table describes the BGP6 configuration commands that cannot be dynamically changed. To activate these commands, you need to reload or restart the device.
Commands
CONFIG, protocol BGP6, enable bgp6
CONFIG, protocol BGP6, disable bgp6
CONFIG, protocol BGP6, add no-receive
CONFIG, protocol BGP6, delete no-receive
CONFIG, protocol BGP6, add/change/delete/move aggregate
CONFIG, protocol BGP6, add/change/delete/move originate-policy
CONFIG, protocol BGP6, add/change/delete/move receive-policy
CONFIG, protocol BGP6, add/change/delete/move send-policy
CONFIG, protocol BGP6, enable compare-med-from-diff-as
CONFIG, protocol BGP6, set ipv6-route-table-scan-timer


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]